Create a repository mapping with descriptions for the project - #1007
Conversation
github-actions
Bot
added
the
documentation
|
Sad to see napari-workshop-template go, it was such a huge help in setting up my own workshops. |
Totally fair! I'm pretty unsure about it, given that it is useful, but its been not maintained long enough that if anything its probably harmful to keep around. Do you think we could reinvigorate with the new napari/workshops strategy? I think you are not the only person that made "community" workshops from the template. Let's definitely move this discussion somewhere else. .. Zulip? napari/napari-workshop-template? I'm not sure I'll let you decide since you have both the most context and experience with it |
TimMonko
left a comment
TimMonko
left a comment
There was a problem hiding this comment.
Discussion with @DragaDoncila during today's community meeting
| - [plugin-cookiecutter](https://github.com/napari/plugin-cookiecutter): early plugin cookiecutter repository. | ||
| - [product-heuristics-2020](https://github.com/napari/product-heuristics-2020): product-heuristics snapshot from 2020. | ||
| - [superqt](https://github.com/napari/superqt): mirror of the upstream `pyapp-kit/superqt` project. | ||
| - [surveys](https://github.com/napari/surveys): Analysis workflows for napari survey data. |
There was a problem hiding this comment.
I DM'd Melissa to determine if she has a local working draft going for this repo, before we archive
There was a problem hiding this comment.
argh sorry I didn't realize this is what you were asking and only now I am reviewing this PR! Yes I do have a local copy, are we archiving just because you have too many things under napari? If so I can keep it under my account just so the analysis is still there (currently on a PR).
DragaDoncila
left a comment
DragaDoncila
left a comment
There was a problem hiding this comment.
Small suggestions here! This can go in ❤️ 🙏
Co-authored-by: Tim Monko <[email protected]> Co-authored-by: Draga Doncila Pop <[email protected]>
for more information, see https://pre-commit.ci
ba650ee to
341986f
Compare
5 participants
Description
It's important we have some kind of map and pulse on our repos. This both helps give us an overview of what is actually happening, and for contributors to know how to help -- especially as we plan to spin out more and more repos from napari (like new plugins and such). This is one of the ways that I struggled so much when contributing early to napari, especially with both the documentation system and the plugin system (and I still feel like I'm learning all the npe2 stuff!)
I did my very best to organize this as much as possible, but of course its quite opinionated and some may have a different idea about active/maintenance/early/backlog. I certainly think giving us an eye on backlog will help us triage even our own stuff.
I also note the following repos in the historical/archive section but they are not yet archived. I would recommend we archive these repos:
napari-scipy2025-workshop
surveys (this one could just be outright deleted)
napari-workshop-template
napari-plugin-engine
napari-language-packs